Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

<managers> node

The <managers> node of the icfconfig.xml file contains a subordinate <manager> node for each of the individual managers that must be started.

A manager is simply a persistent procedure that will be run persistently by the Configuration File Manager. The object code for the manager must be accessible via the PROPATH of the session that is running this code.

Each <manager> node contains up to three nodes of its own:

<cManagerName> — The name of the manager, derived from one of two places: gsc_manager_type.manager_type_code or a concatenation of gsc_service_type.service_type_code and the word ConnectionManager. If the manager is a Service Type Manager, the latter mechanism is used to derive the manager name; otherwise the former method is used.
<cFileName> — The name of the procedure to be instantiated as a manager. The value of this field is derived from the concatenation of gsc_object.object_path, a forward slash, and gsc_object.object_filename.
<cHandleName> — A code that indicates a static variable into which the handle of the manager should be stored. Valid values for this field are shown in Table C–2.

Table C–2: Manager static handle codes

Handle code	Handle definition
NON	No StaticHandle Available (default).
AS	gshAstraAppServer—The Default AppServer.
SM	gshSessionManager—Session manager.
SEM	gshSecurityManager—Security manager.
PM	gshProfileManager—Profile manager.
RM	gshRepositoryManager—Repository manager.
TM	gshTranslationManager—Localization manager.
WM	gshWebManager—Web manager.
GM	gshGenManager—General manager.
FM	gshFinManager—Reserved for backward compatibility.
AM	gshAgnManager—Reserved for backward compatibility.
AU	appSrvUtils—Reserved for backward compatibility.